Pedal's Feedback class had a specifier field defined (with documentation) to uniquely identify feedback instances by their conditions — but TIFA and syntactic assertion feedbacks never populated it, making the field useless for those tool categories.

Changes

pedal/tifa/feedbacks.py

All TIFA feedback classes now set self.specifier before calling super().__init__():

• Name-based feedbacks (variable/function/class): specifier = name — covers unused_variable, initialization_problem, overwritten_variable, read_out_of_scope, recursive_call, incorrect_arity, parameter_type_mismatch, and others
• Location-based feedbacks (no identifying name): specifier = str(location) — covers action_after_return, unconnected_blocks, type_change_append, etc.
• incompatible_types: specifier = op_name (the operation description, e.g. "addition")
• recursive_call: extracts name.name since the caller passes a State object rather than a plain string

pedal/assertions/syntactic.py

• RequireAssertionFeedback / RejectAssertionFeedback: specifier = code
• reject_code_regex / require_code_regex: specifier = pattern

tests/test_tifa.py

Added TestSpecifiers with 15 tests verifying specifier values across the main TIFA feedback types:

tifa = pedal.tifa.Tifa()
result = tifa.process_code('a = 0')
assert result.issues['unused_variable'][0].specifier == 'a'

tifa = pedal.tifa.Tifa()
result = tifa.process_code('def f(x: int): return x\nf("hello")')
assert result.issues['parameter_type_mismatch'][0].specifier == 'x'